Assessor Resource

ICTPRG506
Design application architecture

Assessment tool

Version 1.0
Issue Date: May 2024


This unit describes the skills and knowledge required to design the structure of software or systems components, and how they interact.

It applies to individuals who may work as software architects, developers, designers, software engineers or programmers responsible for designing, and building, solution architecture.

No licensing, legislative or certification requirements apply to this unit at the time of publication.

You may want to include more information here about the target group and the purpose of the assessments (eg formative, summative, recognition)


Evidence Required

List the assessment methods to be used and the context and resources required for assessment. Copy and paste the relevant sections from the evidence guide below and then re-write these in plain English.

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Gather and confirm the architecture requirements

1.1 Gather information regarding the architectural requirements

1.2 Establish and document the architectural requirements

2. Design layered architecture

2.1 Separate the areas of concern into logical layers

2.2 Determine cross-cutting concerns

2.3 Define the system into components

2.4 Identify the responsibilities of each component

2.5 Identify the interconnections between components

3. Plan a strategy to re-use components

3.1 Determine an appropriate strategy for communicating with external systems

3.2 Interact with existing legacy components

4. Design for globalisation and localisation

4.1 Determine culture specific information

4.2 Consider database design features

4.3 Select the appropriate user interface

4.4 Develop a software product for worldwide distribution

4.5 Develop a software product for a specific country

Evidence of the ability to:

design layered applications to increase application performance, scalability and re-usability

create flexible and configurable applications, and adapt these to suit different locales

adapt a software product to a particular language, and culture, of the target market.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

outline the principles of database design

outline current software development methodologies

explain object-oriented programming and its role in application architecture

describe the software development life cycle.

Gather evidence to demonstrate consistent performance in conditions that are safe and replicate the workplace. Noise levels, production flow, interruptions and time variances must be typical of those experienced in the programming and software development industry, and include access to:

both functional and non-functional requirements

the tools to design software architecture

specific information for the target culture, or language

the appropriate learning and assessment support, when required.

Assessors must satisfy NVR/AQTF assessor requirements.

Submission Requirements

List each assessment task's title, type (eg project, observation/demonstration, essay, assingnment, checklist) and due date here

Assessment task 1: [title]      Due date:

(add new lines for each of the assessment tasks)

Assessment Tasks

Copy and paste from the following data to produce each assessment task. Write these in plain English and spell out how, when and where the task is to be carried out, under what conditions, and what resources are needed. Include guidelines about how well the candidate has to perform a task for it to be judged satisfactory.

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Gather and confirm the architecture requirements

1.1 Gather information regarding the architectural requirements

1.2 Establish and document the architectural requirements

2. Design layered architecture

2.1 Separate the areas of concern into logical layers

2.2 Determine cross-cutting concerns

2.3 Define the system into components

2.4 Identify the responsibilities of each component

2.5 Identify the interconnections between components

3. Plan a strategy to re-use components

3.1 Determine an appropriate strategy for communicating with external systems

3.2 Interact with existing legacy components

4. Design for globalisation and localisation

4.1 Determine culture specific information

4.2 Consider database design features

4.3 Select the appropriate user interface

4.4 Develop a software product for worldwide distribution

4.5 Develop a software product for a specific country

Evidence of the ability to:

design layered applications to increase application performance, scalability and re-usability

create flexible and configurable applications, and adapt these to suit different locales

adapt a software product to a particular language, and culture, of the target market.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

outline the principles of database design

outline current software development methodologies

explain object-oriented programming and its role in application architecture

describe the software development life cycle.

Gather evidence to demonstrate consistent performance in conditions that are safe and replicate the workplace. Noise levels, production flow, interruptions and time variances must be typical of those experienced in the programming and software development industry, and include access to:

both functional and non-functional requirements

the tools to design software architecture

specific information for the target culture, or language

the appropriate learning and assessment support, when required.

Assessors must satisfy NVR/AQTF assessor requirements.
Copy and paste from the following performance criteria to create an observation checklist for each task. When you have finished writing your assessment tool every one of these must have been addressed, preferably several times in a variety of contexts. To ensure this occurs download the assessment matrix for the unit; enter each assessment task as a column header and place check marks against each performance criteria that task addresses.

Observation Checklist

Tasks to be observed according to workplace/college/TAFE policy and procedures, relevant legislation and Codes of Practice Yes No Comments/feedback
Gather information regarding the architectural requirements 
Establish and document the architectural requirements 
Separate the areas of concern into logical layers 
Determine cross-cutting concerns 
Define the system into components 
Identify the responsibilities of each component 
Identify the interconnections between components 
Determine an appropriate strategy for communicating with external systems 
Interact with existing legacy components 
Determine culture specific information 
Consider database design features 
Select the appropriate user interface 
Develop a software product for worldwide distribution 
Develop a software product for a specific country 

Forms

Assessment Cover Sheet

ICTPRG506 - Design application architecture
Assessment task 1: [title]

Student name:

Student ID:

I declare that the assessment tasks submitted for this unit are my own work.

Student signature:

Result: Competent Not yet competent

Feedback to student

 

 

 

 

 

 

 

 

Assessor name:

Signature:

Date:

Assessment Record Sheet

ICTPRG506 - Design application architecture

Student name:

Student ID:

Assessment task 1: [title] Result: Competent Not yet competent

(add lines for each task)

Feedback to student:

 

 

 

 

 

 

 

 

Overall assessment result: Competent Not yet competent

Assessor name:

Signature:

Date:

Student signature:

Date: